Dynamic refresh rate switching

ABSTRACT

Dynamic refresh rate (DRR) switching is used to dynamically update a refresh rate of content presented on an interface. When a first application and a second application are presented on a user interface at a first refresh rate; a request may be received to temporarily boost the first refresh rate to a second, higher, refresh rate. DRR switching is initiated as the first refresh rate is temporarily boosted to a second refresh rate. Applications that are opted in to the second refresh rate receive signals to refresh content at the second refresh rate, while applications that are not opted in to the second refresh rate receive signals to refresh content at a virtualized refresh rate that matches the first refresh rate. Thus, the first application refreshes content at the first refresh rate and the second application refreshes content at the second, higher refresh rate, providing a smooth user experience without unnecessarily utilizing power consumption.

CROSS-REFERENCE TO RELATED APPLICATION

This non-provisional utility application is a continuation of U.S.application Ser. No. 17/738,876 entitled “Dynamic Refresh RateSwitching” and filed on May 6, 2022, wish is incorporated herein in itsentirety by reference.

BACKGROUND

Some modern electronic computing devices include display devices, suchas a display screen, that are capable of executing at high-frequencyrefresh rates and dynamically switching between higher and lower refreshrates depending on the application presently presented on the screen.For example, some display screens are capable of executing at or aboverates of 120 Hz. While increased refresh rates improve the userexperience on such devices, additional power is consumed when comparedto executing at lower refresh rates, such as 60 Hz.

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

Examples and implementations disclosed herein are directed to systemsand methods that dynamically update a refresh rate of content presentedby one or more applications on at least one user interface. For example,the system comprises at least one processor, a first application and asecond application, at least one user interface configured to presentthe first application and the second application executing at a firstrefresh rate, and at least one memory storing instructions. Whenexecuted by the processor, the instructions cause the processor to,responsive to receiving a request from the second application totemporarily boost the first refresh rate, determine to temporarily boostthe first refresh rate to a second refresh rate, wherein the secondrefresh rate is higher than the first refresh rate, control a scheduler,implemented on the at least one processor, to identify the secondapplication as opted in to the second refresh rate and identify thefirst application as not opted in to the second refresh rate, controlthe scheduler to transmit a first signal to the first application torefresh first content presented on the user interface at the firstrefresh rate, wherein the first signal is transmitted in accordance witha virtualized refresh rate, control the scheduler to transmit a secondsignal to the second application to refresh second content presented onthe user interface at the second refresh rate, wherein the second signalis transmitted in accordance with a non-virtualized refresh rate, andcontrol the first application to refresh the first content at the firstrefresh rate upon receipt of the first signal and the second applicationto refresh the second content at the second refresh rate upon receipt ofthe second signal.

BRIEF DESCRIPTION OF THE DRAWINGS

The present description will be better understood from the followingdetailed description read in light of the accompanying drawings,wherein:

FIG. 1 is a block diagram illustrating an example computing device forimplementing various examples of the present disclosure;

FIG. 2 is a block diagram illustrating an example computing device forimplementing various examples of the present disclosure;

FIG. 3 is a timeline diagram illustrating a timeline for dynamic refreshrate switching according to various examples of the present disclosure;

FIG. 4 is a flow chart illustrating a computer-implemented method for anexample of dynamic refresh rate switching according to various examplesof the present disclosure;

FIGS. 5A and 5B are a flow chart illustrating a computer-implementedmethod for another example of dynamic refresh rate switching accordingto various examples of the present disclosure;

FIG. 6 illustrates an example system including applications displayed onmore than one display according to various examples of the presentdisclosure; and

FIG. 7 is a flow chart illustrating a computer-implemented method ofdynamic refresh rate switching according to various examples of thepresent disclosure.

Corresponding reference characters indicate corresponding partsthroughout the drawings. In FIGS. 1 to 7 , the systems are illustratedas schematic drawings. The drawings may not be to scale.

DETAILED DESCRIPTION

The various implementations and examples will be described in detailwith reference to the accompanying drawings. Wherever possible, the samereference numbers will be used throughout the drawings to refer to thesame or like parts. References made throughout this disclosure relatingto specific examples and implementations are provided solely forillustrative purposes but, unless indicated to the contrary, are notmeant to limit all examples.

As described herein, the displays of modern devices and monitors arecapable of refreshing at higher frequency rates, up to 120 Hz or higher,and dynamically updating the refresh rates by switching between higherand lower refresh rates depending on the application presently presentedon the screen. Higher refresh rates provide smoother transitions, whichimproves the user experience. However, some applications may beincompatible with higher refresh rates, or, due to the nature of theapplication, the user experience is minimally, or not at all, improvedby executing on the higher refresh rate. In these scenarios, negligiblebenefit is provided in comparison to the cost of additional power beingconsumed to refresh at the higher refresh rate.

For some devices, such as those with relatively smaller screens thattypically display only a single application at a time, this presentslittle challenge. In this case, the screen presents the displayedapplication in the best refresh rate for the particular application.However, in some instances, larger screens may present multipleapplications at a single time. This presents additional challengesbecause some applications are most advantageously presented at a higherrefresh rate than others.

Current solutions address these challenges by changing the duration offrames and frequency of all applications at the operating system level.For example, gaming applications synchronize frame rates with therefresh rate of the monitor. However, these solutions fail to transitionbetween two constant refresh rates. While these solutions change betweenrefresh rates, the refresh rates are not constant between multipleframes. Other solutions utilize an application programming interface(API) to select a specific refresh rate for the lifecycle of theapplication or by the operating system itself. For example, a firstapplication may request to execute at a high refresh rate for theduration that the application is open. Where another application isexecuting at one refresh rate, the operating system also changes therefresh rate for the content of the second application, which affectsthe user experience on the second application. Another solution controlsrefresh rates of the screen only when the system is idle, which fails toimprove the user experience or balance the user experience with powerconsumption.

The present application addresses these deficiencies by providing adynamic refresh rate (DRR) process that dynamically changes, orswitches, the refresh rate of content presented on a user interfaceseamlessly and dynamically between multiple refresh rates based on thetype of content shown and the applications requesting a particularrefresh rate. This dynamic switching supports multiple applications on asingle interface at one time that request different refresh rates.Accordingly, the present application enables dynamic switching bytemporarily boosting the refresh rate of all active applications, i.e.,applications actively producing new frames, on the display to the higherrefresh rate while maintaining virtual refresh rates for applicationsthat are unable to refresh at the higher refresh rate or have opted notto execute at a lower refresh rate. This enables applications to controlwhen additional speeds are observed and to request a higher refreshrate, such as for a specific animation or animations.

As referenced herein, the refresh rate of a respective application iscontrolled by the frequency at which a vertical blanking interval(vblank) is received. A vblank is pulse, or signal, sent to eachexecuting application at a specified frequency to indicate a new frame.Timing information for the vblank(s) sent to an application iscontrolled by a clock, such as a presentation clock or a compositorclock. Each application uses the clock to map when to wake to receive anext vblank indicating to refresh the content the application presents.

Various examples of the present disclosure provide vblanks that may besent on a virtualized frequency or a non-virtualized frequency. Asreferenced herein, non-virtualized refers to an actual, or real,frequency at which content presented on a user interface is refreshedand virtualized refers to an alternative frequency, different from thenon-virtualized frequency, at which content presented on a userinterface may be refreshed. For example, applications capable ofrefreshing content at an increased rate may receive vblanks to refreshat a non-virtualized frequency, while applications not capable ofrefreshing content at the increased rate may receive vblanks to refreshat the virtualized frequency to avoid receiving vblanks to refreshcontent at a higher rate than the application is capable of.

Various examples of the present disclosure recognize and take intoaccount the advantages of switching between a higher refresh rate and alower refresh rate in real-time. For example, a baseline refresh ratemay be a refresh rate at an initial frequency at which all executingapplications are capable of executing. When refreshing at the baselinerefresh rate, the system or application may request a boost totemporarily run, or execute, at the higher refresh rate. When thetemporary boost is implemented, applications that are capable of, andopted in to, the higher, non-virtualized frequency temporarily receivevblanks at the non-virtualized frequency while applications that are notcapable of refreshing at the higher, non-virtualized frequency and/orhave not opted in to the higher, non-virtualized frequency receivevblanks at the virtualized frequency, which mirrors the initialfrequency for the baseline refresh rate. By providing only the temporaryboost, the power efficiency of the system as a whole is improved whilesimultaneously providing smooth refresh rate experiences to the userwhen doing so is advantageous. This limits erratic application behaviorduring refresh rate changes so that vblanks will obfuscate changes bydefault, allowing some applications to opt in to be notified of therefresh rate when the refresh rate changes. In other words, theapplications may receive clock notifications and produce frames at abaseline, lower refresh rate and then receive clock notifications andproduce frames at the higher refresh rate as the refresh ratedynamically switches to the higher refresh rate.

As referenced herein, a refresh rate of a display, such as a monitor, isthe number of times per second that the content is refreshed on thedisplay. For example, a display refreshing at 60 Hz will be updatedsixty times per second, a display refreshing at 120 Hz will be updatedat 120 times per second, and so forth. The refresh rate determines howsmoothly motion appears on the display. For example, where the contenton the display is a gaming application that includes fast-moving action,a higher refresh rate may improve the overall gaming experience of theuser by better keeping up with the action. A higher refresh rate mayalso improve the user experience by implementing smoother motion whenbrowsing the web or using a digital pen to write or draw on the display.

As referenced herein, the terms lower refresh rate and higher refreshrate should be understood to be relative terms. For example, a lowerrefresh rate may refer to a refresh rate of 60 Hz and a higher refreshrate may refer to a refresh rate of 120 Hz. 60 Hz is a lower refreshrate than 120 Hz, and 120 Hz is a higher refresh rate than 60 Hz.However, the specific refresh rates of 60 Hz and 120 Hz are provided asexamples only and should not be construed as limiting. The lower refreshrate may be higher or lower than 60 Hz and the higher refresh rate maybe higher or lower than 120 Hz without departing from the scope of thepresent disclosure.

In order to temporarily boost the refresh rate of all activeapplications while maintaining the virtual refresh rates forapplications executing at a lower speed, the present disclosureimplements virtualized rates and non-virtualized rates for differentapplications. As referenced herein, a virtualized rate is the refreshrate that is provided to applications executing at a lower speed,whereas a non-virtualized rate is the refresh rate of all activeapplications, exclusive of applications executing at the virtualizedrefresh rate. The virtualized rate is provided to applications executingat the lower speed in order to enable refreshing of the content at arate compatible with the application's capabilities and proper behaviorof the user interface throughout the period of temporary boosting, sothat these applications do not receive instructions to execute at speedsgreater than their capabilities.

As referenced herein, boosting the refresh rate refers to increasing therefresh rate of frames presented on a display, monitor, or interfacefrom an original, unboosted refresh rate. The boosted refresh rate is aninteger multiple of the original, unboosted refresh rate. For example,where the original refresh rate is 60 Hz, a boosted refresh may be 120Hz, 180 Hz, and so forth. Boosting the refresh rate to an increasedrefresh rate includes increasing a frequency at which vblanks aredelivered to an application, or applications, to refresh contentpresented on the display by the application. A temporary boost of therefresh rate is referred to herein as dynamically switching the refreshrate.

As referenced herein, the virtualized rates and non-virtualized ratesare implemented by sending either a virtualized vblank or anon-virtualized vblank to each application at the different refreshrates. As referenced herein, a vblank is a signal provided separately toeach application indicating a new frame. A virtualized vblank isprovided at the same time and at the same rate for each applicationexecuting at the virtualized rate and a non-virtualized vblank isprovided at the same time and at the same rate for each applicationexecuting at the non-virtualized rate.

Accordingly, the present application enables the device's power savingsrate to remain competitive with the dynamically changing high refreshrates while enabling a user to control boosting availability as needed.Adoption of automatically boosted API sets and a predictable boostingexperience and capabilities across panels is improved. The presentdisclosure may be further implemented while the system is executed usinga single monitor or more than one monitor.

FIG. 1 is a block diagram illustrating an example computing device 100for implementing aspects disclosed herein and is designated generally ascomputing device 100. Computing device 100 is but one example of asuitable computing environment and is not intended to suggest anylimitation as to the scope of use or functionality of the examplesdisclosed herein. Neither should the computing device 100 be interpretedas having any dependency or requirement relating to any one orcombination of components/modules illustrated.

The examples disclosed herein may be described in the general context ofcomputer code or machine- or computer-executable instructions, such asprogram components, being executed by a computer or other machine.Program components include routines, programs, objects, components, datastructures, and the like that refer to code, performs particular tasks,or implement particular abstract data types. The disclosed examples maybe practiced in a variety of system configurations, including servers,personal computers, laptops, smart phones, servers, virtual machines(VMs), mobile tablets, hand-held devices, consumer electronics,specialty computing devices, etc. The disclosed examples may also bepracticed in distributed computing environments when tasks are performedby remote-processing devices that are linked through a communicationsnetwork.

The computing device 100 includes a bus 110 that directly or indirectlycouples the following devices: computer-storage memory 112, one or moreprocessors 114, one or more presentation components 116, I/O ports 118,I/O components 120, a power supply 122, and a network component 124.While the computing device 100 is depicted as a seemingly single device,multiple computing devices 100 may work together and share the depicteddevice resources. For example, memory 112 is distributed across multipledevices, and processor(s) 114 is housed with different devices. Bus 110represents what may be one or more busses (such as an address bus, databus, or a combination thereof). Although the various blocks of FIG. 1are shown with lines for the sake of clarity, delineating variouscomponents may be accomplished with alternative representations. Forexample, a presentation component such as a display device is an I/Ocomponent in some examples, and some examples of processors have theirown memory. Distinction is not made between such categories as“workstation,” “server,” “laptop,” “hand-held device,” etc., as all arecontemplated within the scope of FIG. 1 and the references herein to a“computing device.”

Memory 112 may take the form of the computer-storage memory devicereferenced below and operatively provide storage of computer-readableinstructions, data structures, program modules and other data for thecomputing device 100. In some examples, memory 112 stores one or more ofan operating system (OS), a universal application platform, or otherprogram modules and program data. Memory 112 is thus able to store andaccess data 112 a and instructions 112 b that are executable byprocessor 114 and configured to carry out the various operationsdisclosed herein. In some examples, memory 112 stores executablecomputer instructions for an OS and various software applications. TheOS may be any OS designed to the control the functionality of thecomputing device 100, including, for example but without limitation:WINDOWS® developed by the MICROSOFT CORPORATION®, MAC OS® developed byAPPLE, INC.® of Cupertino, Calif, ANDROID™ developed by GOOGLE, INC.® ofMountain View, California, open-source LINUX®, and the like.

By way of example and not limitation, computer readable media comprisecomputer-storage memory devices and communication media.Computer-storage memory devices may include volatile, nonvolatile,removable, non-removable, or other memory implemented in any method ortechnology for storage of information such as computer-readableinstructions, data structures, program modules, or the like.Computer-storage memory devices are tangible and mutually exclusive tocommunication media. Computer-storage memory devices are implemented inhardware and exclude carrier waves and propagated signals.Computer-storage memory devices for purposes of this disclosure are notsignals per se. Example computer-storage memory devices include harddisks, flash drives, solid state memory, phase change random-accessmemory (PRAM), static random-access memory (SRAM), dynamic random-accessmemory (DRAM), other types of random-access memory (RAM), read-onlymemory (ROM), electrically erasable programmable read-only memory(EEPROM), flash memory or other memory technology, compact diskread-only memory (CD-ROM), digital versatile disks (DVD) or otheroptical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other non-transmissionmedium that may be used to store information for access by a computingdevice. In contrast, communication media typically embody computerreadable instructions, data structures, program modules, or the like ina modulated data signal such as a carrier wave or other transportmechanism and include any information delivery media.

The computer-executable instructions may be organized into one or morecomputer-executable components or modules. Generally, program modulesinclude, but are not limited to, routines, programs, objects,components, and data structures that perform particular tasks orimplement particular abstract data types. Aspects of the disclosure maybe implemented with any number an organization of such components ormodules. For example, aspects of the disclosure are not limited to thespecific computer-executable instructions or the specific components ormodules illustrated in the figures and described herein. Other examplesof the disclosure may include different computer-executable instructionsor components having more or less functionality than illustrated anddescribed herein. In examples involving a general-purpose computer,aspects of the disclosure transform the general-purpose computer into aspecial-purpose computing device, CPU, GPU, ASIC, system on chip (SoC),or the like for provisioning new VMs when configured to execute theinstructions described herein.

Processor(s) 114 may include any quantity of processing units that readdata from various entities, such as memory 112 or I/O components 120.Specifically, processor(s) 114 are programmed to executecomputer-executable instructions for implementing aspects of thedisclosure. The instructions may be performed by the processor 114, bymultiple processors 114 within the computing device 100, or by aprocessor external to the client computing device 100. In some examples,the processor(s) 114 are programmed to execute instructions such asthose illustrated in the flow charts discussed below and depicted in theaccompanying figures. Moreover, in some examples, the processor(s) 114represent an implementation of analog techniques to perform theoperations described herein. For example, the operations are performedby an analog client computing device 100 and/or a digital clientcomputing device 100.

Presentation component(s) 116 present data indications to a user orother device. Example presentation components include a display device,speaker, printing component, vibrating component, etc. One skilled inthe art will understand and appreciate that computer data may bepresented in a number of ways, such as visually in a graphical userinterface (GUI), audibly through speakers, wirelessly between computingdevices 100, across a wired connection, or in other ways. I/O ports 118allow computing device 100 to be logically coupled to other devicesincluding I/O components 120, some of which may be built in. Example I/Ocomponents 120 include, for example but without limitation, amicrophone, joystick, game pad, satellite dish, scanner, printer,wireless device, etc.

The computing device 100 may communicate over a network 130 via networkcomponent 124 using logical connections to one or more remote computers.In some examples, the network component 124 includes a network interfacecard and/or computer-executable instructions (e.g., a driver) foroperating the network interface card. Communication between thecomputing device 100 and other devices may occur using any protocol ormechanism over any wired or wireless connection. In some examples,network component 124 is operable to communicate data over public,private, or hybrid (public and private) using a transfer protocol,between devices wirelessly using short range communication technologies(e.g., near-field communication (NFC), Bluetooth™ brandedcommunications, or the like), or a combination thereof. Networkcomponent 124 communicates over wireless communication link 126 and/or awired communication link 126 a across network 130 to a cloud environment128. Various different examples of communication links 126 and 126 ainclude a wireless connection, a wired connection, and/or a dedicatedlink, and in some examples, at least a portion is routed through theInternet.

The network 130 may include any computer network or combination thereof.Examples of computer networks configurable to operate as network 130include, without limitation, a wireless network; landline; cable line;digital subscriber line (DSL): fiber-optic line; cellular network (e.g.,3G, 4G, 5G, etc.); local area network (LAN); wide area network (WAN);metropolitan area network (MAN); or the like. The network 130 is notlimited, however, to connections coupling separate computer units.Rather, the network 130 may also include subsystems that transfer databetween servers or computing devices. For example, the network 130 mayalso include a point-to-point connection, the Internet, an Ethernet, anelectrical bus, a neural network, or other internal system. Suchnetworking architectures are well known and need not be discussed atdepth herein.

As described herein, the computing device 100 may be implemented as oneor more servers. The computing device 100 may be implemented as a system200 or in the system 200 as described in greater detail below.

FIG. 2 is a block diagram illustrating an example computing device forimplementing various examples of the present disclosure. The system 200may include the computing device 100. In some implementations, thesystem 200 includes a cloud-implemented server that includes each of thecomponents of the system 200 described herein. In some implementations,the system 200 is presented as a single computing device that containseach of the components of the system 200. For example, the system 200may include a laptop computer containing each of the componentsdescribed herein. In other implementations, the system 200 includesmultiple devices. For example, the system 200 may include a computerconnected to one or more monitors utilized as the user interface 216.

The system 200 includes a memory 202, a processor 208, a communicationsinterface 210, a data storage device 212, a user interface 216, and ascheduler 218. The memory 202 stores instructions 204 executed by theprocessor 208 to control the communications interface 210, the userinterface 216, and the scheduler 218. The memory 202 further storesdata, such as one or more applications 206. An application 206 is aprogram designed to carry out a specific task on the system 200. Forexample, the applications 206 may include, but are not limited to,drawing applications, paint applications, web browser applications,messaging applications, navigation/mapping applications, word processingapplications, game applications, an application store, applicationsincluded in a suite of productivity applications such as calendarapplications, instant messaging applications, document storageapplications, video and/or audio call applications, and so forth, andspecialized applications for a particular system 200. The applications206 may communicate with counterpart applications or services, such asweb services. In an example, the applications 206 represent downloadedclient-side applications that correspond to server-side servicesexecuting in a cloud.

The processor 208 executes the instructions 204 stored on the memory 202to execute various functions of the system 200. For example, theprocessor 208 controls the communications interface 210 to transmit andreceive various signals and data, controls the data storage device 212to store data 214, controls the user interface 216 to display one ormore client-side versions of the applications 206, and controls thescheduler 218 to control the dynamic refresh rate switching, i.e.,temporary boosting, of the applications 206 displayed on the userinterface 216.

In some implementations, the processor 208 receives and logs requestsfrom one or more of the applications 206 and/or the operating system ofthe system 200. For example, instructions for the operating system maybe included within the instructions 204. The instructions 204 may, insome examples, manage the refresh rate, including sending requests toboost or unboost the refresh, on behalf of the one or more applications206. In another example, an application 206 may request to temporarilyboost the refresh rate of the user interface 216 from an originalrefresh rate to an increased refresh rate, request to unboost therefresh rate of the user interface 216, inquire to the processor 208whether the application 206 has an active boosting request, and soforth. As described herein, boosting the refresh rate from the originalrefresh rate to the boosted refresh rate includes increasing a frequencyat which vblanks are delivered to an application, or applications, torefresh content presented on the user interface 216 by the application206.

The data storage device 212 stores data 214. The data 214 may includeany data, including data related to dynamic refresh rate switching forthe applications 206 presented on the user interface 216 and/or otherdata stored on the system 200. For example, the data 214 may includeversion history of each particular application 206. The scheduler 218may use the data 214 to determine which of the applications 206 may bepresented on the user interface 216 at a boosted refresh rate and whichof the applications 206 are to be presented on the user interface 216 atan original, baseline refresh rate.

The user interface 216 presents one or more applications 206. The userinterface 216 may be presented on a display 215. For example, the userinterface 216 may be presented on a display 215, such as or a monitor,that presents one or more applications 206 at a time. The display 215may be an in plane switching (IPS) liquid-crystal display (LCD), an LCDwithout IPS, an organic light-emitting diode (OLED) screen, or any othersuitable type of display. In some implementations, the display 215includes a touch screen such that the user interface 216 may directlyreceive an input, such as from a stylus or from the finger of a user ofthe system 200. The display 215 supports various interactions, such aspanning, scrolling, zooming in, zooming out, inking, and so forth. Asreferenced herein, inking refers to the process of interacting with anapplication 206 by contacting the display 215, such as with a stylus orthe finger of a user. For example, the application 206 may be a paint ordrawing application where the user draws on the user interface 216. Themarkings made on the display 215 appear on the user interface 216 ascontent presented by the application 206.

In some implementations, the display 215 includes a single display, suchas a single monitor. In other implementations, the display 215 includesmultiple displays, such as more than one monitor. Where the display 215includes multiple displays, the displays may be extended such thatcontent may be displayed on both displays, duplicated such that the samecontent is displayed on each display, or content may be displayed ononly one of the displays. Although the display 215 presenting the userinterface 216 is shown in FIG. 2 as implemented on the system 200,various examples are possible. For example, the display 215 may includeone or more monitors connected to the system 200 via wired or wirelessmethods, as illustrated in FIG. 6 and described in greater detail below.Examples of wired methods include a high-definition multimedia interface(HDMI) cable, a universal serial bus (USB) cable such as a USB-C cable,a digital visual interface (DVI) cable, or any other suitable cable forconnecting a monitor to the system 200. Examples of wireless methodsinclude Bluetooth™ connection, a wireless internet connection such asWi-Fi™, or any other suitable method.

Each application 206 displays content 207 corresponding to theapplication 206 on the user interface 216 presented on the display 215.For example, the first application 206 a displays content 207 a, thesecond application 206 b displays content 207 b, and the thirdapplication 206 n displays content 207 n.

As shown in FIG. 2 , the user interface 216 displays the firstapplication 1 206 a, the second application 2 206 b, and the thirdapplication 3 206 n. The user interface 216 may display any number ofapplications 206 without departing from the scope of the presentdisclosure. For example, the user interface 216 may display oneapplication 206, two applications 206, or more than two applications 206at a time. Multiple applications 206 may be displayed in variousconfigurations. For example, the application 1 206 a may be displayedside by side with the application 2 206 b such that no overlapping ispresent between the application 1 206 a and the application 2 206 b andeach application is fully visible on the user interface 216. As anotherexample, the application 1 206 a may be displayed with the application 2206 b such that the application 1 206 a overlaps the application 2 206b, or such that the application 2 206 b overlaps the applications 1 206a. In some implementations, one or more of the applications 206 may bevisible in the foreground of the user interface 216 while otherapplications 206 are executing in the background but not presented, ordisplayed, on the user interface 216.

In some examples, the user interface 216 is configured with manufacturersettings that support or do not support the temporary boosting of therefresh rate for the particular user interface 216. Some examples of auser interface 216 support a maximum refresh rate that is lower than theboosted refresh rate for one or more of the applications 206. In theseexamples, the user interface 216 does not support the boosted refreshrate and no distinction is made between a boosted refresh rate and avirtualized refresh rate. However, it should be understood that althougha particular monitor may be compatible with dynamically refreshingrates, the availability of temporarily boosting the refresh rate isdependent upon the system 200, particularly the operating system of thesystem 200 executed by the processor 208.

In implementations where more than one user interface 216 isimplemented, such as when two monitors are concurrently presentingcontent of the system 200, the determination of whether boosting isavailable depends on which of the user interfaces 216 is characterizedas the primary display, or target. The primary user interface 216 may beselected by a user or may be automatically selected by the processor208. Various examples are possible when multiple monitors presentcontent simultaneously. Where each monitor is compatible with boostingthe refresh rate, boosting is performed as described herein. Where noneof the implemented monitors are compatible with boosting, boosting ofthe refresh rate as described herein is unavailable. Where the primarymonitor is compatible with boosting but other monitors are notcompatible with boosting, boosting is performed as described herein andall applications 206 presented on monitors which are not compatible withboosting will refresh on the virtualized frequency 224, described ingreater detail below. Where the primary monitor is not compatible withboosting but other monitors are compatible with boosting, boosting isnot available for the applications 206 presented on any of the monitors.Thus, each monitor displays frames rendered at rates according tocapabilities.

In other examples, the display 215 is configured to support varyingrefresh rates up to and including the boosted refresh rate. For example,the display 215 may support multiple refresh rates, such as a highrefresh rate and a low refresh rate. In some implementations, the highrefresh rate is 120 Hz or higher, though various implementations arepossible. In some implementations, the low refresh rate is 60 Hz, thoughvarious implementations are possible. As referenced herein, the highrefresh rate may be an integer multiple greater than the lower refreshrate. For example, where the lower refresh rate is 60 Hz, the higherrefresh rate may be 120 Hz, or twice as high as the lower refresh rate.In another example, where the lower refresh rate is 60 Hz, the higherrefresh rate may be 180 Hz, or three times as high as the lower refreshrate. It should be understood that the various examples of refresh ratesdescribed herein should not be construed as limiting. Variousimplementations are possible. More than two refresh rates may be used,the lower refresh rate may be higher or lower than 60 Hz, and the higherrefresh rate may be higher or lower than 120 Hz without departing fromthe scope of the present disclosure.

The scheduler 218 may be a portion of the operating system of the system200 and implemented when the instructions 204 are executed by theprocessor 208. The scheduler 218 includes a virtual synchronization(VSync) framework 220 layer that enables a constant pulse, or signal, tobe sent to the applications 206 a, 206 b, 206 n to refresh at specifiedrates. In some implementations, the pulse is referred to as a vblank.The vblank is a signal provided separately to each applicationindicating a new frame. In some examples, vblanks are initially providedat a baseline refresh rate. The baseline refresh rate is a refresh rateat an initial frequency at which all executing applications are capableof executing.

In some examples vblanks may be sent on either a non-virtualizedfrequency 222 or a virtualized frequency 224. The non-virtualizedfrequency 222 is the actual frequency at which the user interface 216 isrefreshed. For example, where the baseline refresh rate is 60 Hz, duringa temporary boost in refresh rate frequency, the boosted frequency maybe 120 Hz. The non-virtualized frequency 222 is 120 Hz, because 120 Hzis the actual frequency at which the user interface 216 is refreshed.Applications 206 executing at the non-virtualized rate, including theapplication(s) 206 that requested the temporary boost, receive a vblankat the non-virtualized frequency 222. As described herein, thevirtualized frequency 224 is a virtual frequency that enablesapplications 206, which have not opted in to run at a higher frequency,to continue operating at the baseline frequency. In this example, thevirtualized frequency 224 matches the baseline frequency of 60 Hz. Inthis way, the virtualized frequency 224 operates to intentionally holdback some applications 206 from refreshing at a higher, i.e.,non-virtualized frequency 222, rate, such as where the particularapplications 206 are not capable of executing at the higher refresh rateor would see no benefit from executing at the higher refresh rate.

In some implementations, the system 200 includes a clock 226. The clock226 may be a presentation, or compositor, clock that controls timinginformation for frames of the applications 206 presented on the userinterface 216. For example, each application 206 may call the clock 226to identify a time at which the application 206 should wake to receive anew vblank in order to refresh the content presented on the userinterface 216. In some implementations, the clock 226 may includedifferent clocks for the non-virtualized frequency 222 and thevirtualized frequency 224. The clock 226 corresponding to thenon-virtualized frequency 222 maps to vblanks expected according to thetemporarily boosted refresh rate, while the clock 226 corresponding thevirtualized frequency 224 maps to vblanks expected according to baselinerefresh rate.

In some implementations, the clock 226 is provided to each of theapplications 206 via an API called by each of the applications 206. Theclock 226, such as the compositor clock API, provides statistics andframe rate control for applications 206 to present on-screen content 207smoothly, at the fastest possible cadence, and may be implemented on avariety of hardware configurations. In some implementations, an API mayprovide a callback interface for the non-virtualized frequency 222 suchas CompositorClock::WaitforVblank and a callback interface for thevirtualized frequency 224 such as theCompositorClock::WaitforVirtualVblank. In another implementation, suchas a raster scan, the clock 226 implements an API such asIDXGIOutput::WaitForVBlank, where a thread is halted until the nextvblank occurs. In this example, the vblank occurs when the raster movesfrom the lower right corner to the upper left corner to begin drawing anext frame.

In some implementations, the processor 208 maintains frame statisticsfor both previous frames and the next expected frame. The framestatistics may include a last frame time, a current composition rate, acurrent time, a time frequency, and a next estimated frame time. Forexample, as illustrated in FIG. 3 below, a frame 313 includes a previousframe, the first frame 311, and a next frame, the third frame 315. Theprocessor 208 may utilize the frame statistics to return an estimatedtime, composition rate, and virtual synchronization count for thefollowing frame. In some implementations, the frame statistics aremapped to the clock 226 to track the time for a previous frame or nextframe. In other implementations, the frame statistics are mapped to avblank, such as a virtual vblank or a non-virtual vblank as described ingreater detail below. The frame statistics may be accessed by anapplication 206 by requesting the frame statistics through an API and,upon receipt of the frame statistics, retrieving a particular frame orrange of frame statistics. In some implementations, the frame statisticsprovided in response to the request includes both refresh counts for thenon-virtualized frequency 222 and the virtualized frequency 224 for theapplication 206 to observe both the actual and the virtual frame rates.

Using a combination of the clock 226, the frame statistics, and requeststo temporarily boost the refresh rate of the user interface 216, eachapplication 206 may request changes to the boosting status of the userinterface 216, wake at the correct time to receive the correct vblankcadence, and observe statistics to predict the next frame timing andunderstand where previous frames landed. Accordingly, applications 206are provided the tools needed to manage boosting. However, someparticular applications 206 may encounter challenges integrating each ofthese tools because of how the particular application 206 separates theinput and user interface threads. For example, applications 206 may wantto boost or change their clock 226 after receiving an input, which willmanage behaviors that are typically executed by a user interface API.

In some implementations, the system 200 includes a queue 228. In someimplementations, the queue 228 is stored on the memory 202. In otherimplementations, the queue 228 is stored on the data storage device 212.The queue 228 stores boosting requests received from one or moreapplications 206. For example, a request is logged and opened in thequeue 228 upon receipt of a boost request from an application 206 andclosed when a request to terminate, or cease, the temporary boost isreceived from the application 206. Accordingly, the queue 228 maycontain one or more open requests at a time. The queue 228 may bescanned by the processor 208 to determine whether to grant requests totemporarily boost the refresh rate or to grant requests to cease thetemporary boost to the refresh rate.

FIG. 3 is a timeline diagram illustrating a timeline for dynamic refreshrate switching according to various examples of the present disclosure.The timeline diagram 300 includes a first application 301 and a secondapplication 310. As shown in the timeline diagram 300, each of the firstapplication 301 and the second application 310 may be versions of theapplication 206 and executing on the user interface 216. For example,the first application 301 may be the first application 206 a and thesecond application 310 may be the second application 206 b.

As shown in the timeline diagram 300, the first application 301 is anapplication which has not opted in to the boosted refresh rate. Forexample, the first application 301 may see minimal or no improvementwhen refreshed at a higher refresh rate. For example, the firstapplication 301 may include, but is not limited to, an application notpresently receiving a user input or an application that does supportrefreshing at an increased frame rate. In contrast, the secondapplication 310 is an application that is opted in to boosted refreshrates, such as a paint or drawing application that responds to a user'sdirect input on the user interface 216. However, these examples areprovided for illustration only and should not be construed as limiting.Various examples may be provided without departing from the scope of thepresent disclosure.

The timeline diagram 300 further includes a timeline 330 that includesintervals every 16 milliseconds (ms). For example, the timeline 330includes intervals at 100 ms, 116 ms, 132 ms, 148 ms, 164 ms, and 180ms. As shown in the timeline diagram 300, each interval of 16 ms isequivalent to a frequency of 60 Hz. In other words, a vblank sent at afrequency of 60 Hz will be delivered every 16 ms. The 60 Hz frequencymay represent the virtualized frequency 222. As shown in the timelinediagram 300, two cycles of 120 Hz are equivalent to the 60 Hz. In otherwords, 120 Hz is a frequency with a rate twice as fast as 60 Hz. The 120Hz frequency may represent the non-virtualized frequency 224. Eachvblank represents the timing that a frame starts, refreshing the content207 the particular application 206 presents on the user interface 216.

As illustrated in FIG. 3 , the first application 301 has not opted in tothe boosted frame rate and therefore operates on the virtualizedfrequency 222 of 60 Hz. For example, the first application 301 may be anapplication that does not support operations at a refresh rate higherthan the virtualized frequency 222, an application that does not supportoperations at a refresh rate up to the non-virtualized frequency 224, oran application that derives minimal or no benefit from operating at thenon-virtualized frequency 224. In contrast, the second application 310has opted in to the boosted refresh rate and therefore operates on thenon-virtualized frequency 224 of 120 Hz.

At each interval, the frame of the respective application refreshes,flips, or updates. For example, the first application 301 includes afirst frame 303, a second frame 305, a third frame 307, and a fourthframe 309. The second application 310 includes a first frame 311, asecond frame 313, a third frame 315, a fourth frame 317, a fifth frame319, a sixth frame 321, a seventh frame 323, an eighth frame 325, aninth frame 327, and a tenth frame 329.

At time=100 ms, a first set of pulses, or signals or vblanks, 332 aresent to each of the first application 301 and the second application310. The first set of vblanks 332 may include a virtualized vblank sentto the first application 301 and a non-virtualized vblank sent to thesecond application 310. Upon receipt of the first set of vblanks, eachof the first application 301 and the second application 310 refresh thecontent 207 displayed on the user interface 216 by updating to the nextrespective frame. For example, the first application 301 updates to afirst frame 303 and the second application 310 updates to a first frame311. Although described herein as first frames 303 and 311, it should beunderstood that the term first is used for reference only and the firstframes 303 and 311 may be preceded in the timeline, before time=100 ms,by other frames.

As shown in the timeline diagram 300, following time=100 ms, the nextnon-virtualized vblank is delivered to the second application 310 thathas opted in to the temporarily boosted refresh rate. For example, asecond vblank 334 is sent to the second application 310 at a frequencyof 120 Hz. It should be understood that because the frequency of 60 Hzis equivalent to a time of 16 ms, and the frequency of 120 Hz is twiceas fast as the frequency of 60 Hz, the frequency of 120 Hz is equivalentto a time of 8 ms. In other words, the virtualized frequency 222 of 60Hz sends a vblank every 16 ms and the non-virtualized frequency 224 of120 Hz sends a vblank every 8 ms. Accordingly, at time=108 ms, thesecond non-virtualized vblank 334 is sent to the second application 310that has opted in to the temporarily boosted refresh rate, and thesecond application 310 refreshes the content 207 displayed on the userinterface 216 and updates to the second frame 313.

Due to the temporary boosting of the refresh rate of the user interface216, the user interface 216 is boosted to the non-virtualized frequency224 of 120 Hz, but the first application 301, which is not opted in tothe boosted refresh rate, continues to operate at the baseline refreshrate of 60 Hz by waking every 16 ms and receiving only virtualizedvblanks. In other words, although the OS for the system 200 operates at120 Hz, the first application 301 wakes and receives only vblankscorresponding to the baseline refresh rate of 60 Hz. This provides powersavings, because additional processing power is not used to refresh theframes of the first application 301 at the higher refresh rate, whileproviding a higher refresh rate, and therefore improved user experience,for applications such as the second application 310 which do see animprovement when refreshed at the higher refresh rate.

At time=116 ms, both the virtualized frequency 222 and thenon-virtualized frequency 224 are scheduled to deliver a vblank, and athird set of vblanks 336 are sent to each of the first application 301and the second application 310. Upon receipt, the first application 301refreshes the content 207 displayed on the user interface 216 andupdates to the second frame 305, and the second application 310refreshes the content 207 displayed on the user interface 216 andupdates to the third frame 315.

The sequence continues for the duration the first application 301 andthe second application 310 are presented on the user interface 216. Forexample, a fourth vblank 338 is sent to the second application 310 attime=124 ms, a fifth vblank 340 is sent to the first application 301 andthe second application 310 at time=132 ms, a sixth vblank 342 is sent tothe second application 310 at time=140 ms, a seventh vblank 344 is sentto the first application 301 and the second application 310 at time=148ms, an eighth vblank 346 is sent to the second application 310 attime=156 ms, a ninth vblank 348 is sent to the first application 301 andthe second application 310 at time=164 ms, a tenth vblank 350 is sent tothe second application 310 at time=172 ms, and an eleventh vblank 352 issent to the first application 301 and the second application 310 attime=180 ms.

As shown in implementation of the timeline diagram 300, where theseventh vblank 344 is sent to the first application 301 and the secondapplication 310 at time=148 ms, the second application 310 refreshes thecontest presented on the user interface 216 from the sixth frame 321 tothe seventh frame 323, but the first application 301 does not update thecontent 207 of the third frame 307. Accordingly, the third frame 307continues until the ninth vblank 348 is sent at time=164 ms. This isbecause the content 207 presented on the user interface 216 at the thirdframe 307 of the first application 301 does not update or change withthe reception of the seventh vblank 344.

The different vblanks are provided to each application 301, 310 based ona location of each particular application within the VSync framework220. For example, each application that has opted in to the boostedrefresh rate receives vblanks according to the non-virtualized frequency222 and each application that has not opted in to the boosted refreshrate receives vblanks according to the virtualized frequency 224.Accordingly, in some implementations the first application 301 mayrepresent each application operating, at the particular time=100 ms, onthe virtualized frequency 224 and the second application 310 mayrepresent each application operating, at the particular time=100 ms, onthe non-virtualized frequency 222.

Accordingly, as shown in the timeline diagram 300, enabling multipleapplications 206 to concurrently execute on a single user interface 216at different refresh rates reduces power consumption, because resourcesare not allocated to shifting the refresh rates for differentapplications 206. For example, rather than expending resources to shiftthe refresh rate for specific applications, each executing application206 receives a vblank at either the virtualized frequency 224 ornon-virtualized frequency 222, depending on whether the application 206is opted in to temporarily boosting the refresh rate. Further,applications 206 executing at the virtualized frequency 224 are able toexecute at an appropriate refresh rate, rather than an acceleratedrefresh rate they are unable to take advantage of and would cause theexpenditure of additional resources due to waking up to receive a newvblank twice as often as when executing at the baseline refresh rate.

It should be understood that the distinction between the non-virtualizedfrequency 224 and the virtualized frequency 224 is introduced upon thedetermination to temporarily boost the refresh rate of the operatingsystem. Until the processor 208 receives a request or requests totemporarily boost the refresh rate, each of the applications 206presented on the user interface 216 refresh at the baseline refreshrate. For example, each of the applications 206 may be presented on theuser interface 216 and refresh at the baseline refresh rate of 60 Hz.Upon receiving one or more requests to boost the refresh rate, theprocessor 208 calls the Vsync framework 220. The scheduler 218determines which applications 206 have opted in to the non-virtualizedfrequency 222 and which applications 206 have not opted in and thereforewill continue to refresh at the baseline refresh rate via thevirtualized frequency 224. Based on the determination to boost therefresh rate and the determination of which applications have opted into the non-virtualized frequency 222 and which applications have notopted in, the scheduler 218 then temporarily boosts the refresh rate asdescribed herein.

As shown in the timeline diagram 300, the boosted refresh rate of 120 Hzprovides the next vblank in 8 ms, rather than 16 ms for the baselineframe rate of 60 Hz. While this reduces latency and improvesperformance, the boosted refresh rate may sometimes introduce a glitchbecause the processor 208 has half the usual amount of time to renderthe next frame. Accordingly, the processor 208 may select to enter aparallel mode when failing to render, or compose, a frame within thetime required to do so. Parallel mode refers to a mode of operationwhere a frame compositor begins rendering for a frame two-vblanks aheadin time, rather than rendering for a frame one-vblank in time. Inparallel mode, the processor 208 trades off an additional frame oflatency in exchange for additional time to render a frame. Thus, theframe compositor has twice the amount of time to render the frame thanit otherwise would, which reduces latency and improves performance ofthe user interface 216. However, due to the extra time required torender each frame, each frame will be presented one frame later thanscheduled.

In some implementations, the processor 208 may select to enter parallelmode for the duration of the temporary boosting of the refresh rate. Forexample, the processor 208 may automatically enter parallel model everytime temporary boosting occurs. The result is higher latency for allcomposed frames, whether presented in the non-virtualized frequency 222or the virtualized frequency 224, but still a smoother experience than arefresh rate of 60 Hz for applications 206 executing on thenon-virtualized frequency 222.

FIG. 4 is a flow chart illustrating a computer-implemented method for anexample of dynamic refresh rate switching according to various examplesof the present disclosure. The operations illustrated in FIG. 4 are forillustration and should not be construed as limiting. Various examplesof the operations may be used without departing from the scope of thepresent disclosure. The operations of the flow chart 400 may be executedby one or more components of the system 200, including the processor208, the scheduler 218, the first application 206 a, and the secondapplication 206 b.

The flow chart 400 begins by the processor 208 executing one or moreapplications 206 on the user interface 216 in operation 401. Forexample, as shown in the flow chart 400, the first application 206 a andthe second application 206 b are each presented on the user interface216. However, it should be understood that more or fewer than twoapplications 206 may be presented on the user interface 216. Asdescribed herein, the user interface 216 may include one or moredisplays, such as monitors, upon which the one or more applications 206are presented, or displayed.

In operation 403, the processor 208 determines to temporarily boost therefresh rate of the user interface 216. The processor 208 may make thedetermination based on the reception of a request from an API of the oneor more applications presented on the user interface 216. For example,where one of the applications 206 receives an input directly on the userinterface 216, the application may send a request to the processor 208to temporarily boost the refresh rate of the user interface 216. Theapplication 206 may call the processor 208 through either a public APIor a private API to request a temporary boost.

In some implementations, the processor 208 determines to temporarilyboost the refresh rate of the user interface 216 based on the receptionof one request to boost the refresh rate. In other implementations, theprocessor 208 aggregates the requests and determines to temporarilyboost the refresh rate of the user interface 216 based on the receptionof a threshold number of requests from applications 206 and APIsreceived and stored in the queue 228. The threshold may be set by theprocessor 208 to ensure that a sufficient quantity of applications 206would be advantaged by temporarily boosting the refresh rate of the userinterface 216. Based on the determination to boost the refresh rate ofthe user interface 216, the processor 208 calls the scheduler 218 toexecute the temporary boost.

In operation 405, the scheduler 218 determines the frequency for eachexecuting application 206. In some implementations, determining thefrequency includes identifying each executing application 206 within theVSync framework 220 as either opted in to the non-virtualized frequency222 or not opted in to the non-virtualized frequency 222 and thereforeoperating under the virtualized frequency 224.

Following the determination of whether each executing application 206 isopted in to the non-virtualized frequency 222 or not opted in to thenon-virtualized frequency 222, the scheduler 218 initiates the temporaryboosting of the refresh rate of the user interface 216. For example, inoperation 407 the scheduler 218 sends a vblank, at an intervalcorresponding to the lower frequency, to applications executing at boththe non-virtualized frequency 222 and the virtualized frequency 224, andthen in operation 409 the scheduler 218 sends a vblank at an intervalcorresponding to the higher frequency to applications executing at onlythe non-virtualized frequency 222. For example, as described withreference to FIG. 3 , at a first time such as 100 ms, a vblank 332 issent to applications 206 executing at the non-virtualized frequency 222and at the virtualized frequency 224; at a second time such as 108 ms, avblank 334 is sent to applications 206 executing at the non-virtualizedfrequency 222 only; and at a third time such as 106 ms, a vblank 336 issent to applications 206 executing at both the non-virtualized frequency222 and the virtualized frequency 224, and so forth. Operations 407 and409 may repeat until the conclusion of the temporary boosting period.

In operation 411, the processor 208 determines to cease temporaryboosting the refresh rate of the user interface 216. In someimplementations, the processor 208 determines to cease the temporaryboosting based on a predetermined period of time expiring. For example,the original determination to temporarily boost the refresh rate inoperation 403 may be a determination to boost the refresh rate for aperiod of time and upon the expiration of the period of time, theprocessor 208 determines to cease the refresh rate boosting. In anotherimplementation, the processor 208 determines to cease the temporaryboosting based on the reception of a request to cease the temporaryboosting from one or more of the applications 206 executing at thenon-virtualized frequency 222. In yet another implementation, theprocessor 208 determines to cease the temporary boosting based on allother boosting requests having been canceled and the processes of thoseapplications 206 remaining active. In other words, the processor 208will accept the request to cease the temporary boosting if and only ifno other boosting requests are open.

In operation 413, the processor 208 controls the user interface 216 toreturn to the original refresh rate and ceases the temporary boosting ofthe refresh rate. In other words, each of the applications 206 presentedon the user interface 216 return to refreshing, or updating, on thebaseline frequency. Following operation 413, each application 206presented on the user interface 216 receives the next vblank at thelower, baseline frequency, which is the same as the virtualizedfrequency 224.

FIGS. 5A and 5B are a flow chart illustrating a computer-implementedmethod for another example of dynamic refresh rate switching accordingto various examples of the present disclosure. The operationsillustrated in FIGS. 5A and 5B are for illustration and should not beconstrued as limiting. Various examples of the operations may be usedwithout departing from the scope of the present disclosure. Theoperations of the flow chart 500 may be executed by one or morecomponents of the system 200, including the processor 208, the scheduler218, the first application 206 a, and the second application 206 b. Itshould be understood that FIG. 5B is a continuation of FIG. 5A and thatcollectively, FIGS. 5A and 5B illustrate the flow chart 500. In someexamples, the flow chart 500 is one particular implementation of theflow chart 400.

The flow chart 500 begins by the processor 208 executing one or moreapplications 206 on the user interface 216 in operation 501. Forexample, as shown in the flow chart 500, the first application 206 a andthe second application 206 b are each presented on the user interface216. However, it should be understood that more or fewer than twoapplications 206 may be presented on the user interface 216. Asdescribed herein, the user interface 216 may include one or moredisplays, such as monitors, upon which the one or more applications 206are presented, or displayed.

In operation 503, the second applications 206 b receives an input. Forexample, the second application 206 b may be a drawing or inkingapplication that receives an input from a stylus or a finger of a userof the system 200. In another example, the second application 206 b mayreceive an input such as scrolling or panning within the secondapplication 206 b. In operation 505, responsive to receiving the input,the second application 206 b sends a request, to the processor 208, totemporarily boost the refresh rate of the user interface 216. Forexample, due to receiving the input, the second application 206 b mayrecognize the potential advantages of refreshing at a higher rate at theparticular time. In operation 507, the processor 208 determines to boostthe refresh rate for the user interface 216, based on receiving therequest to temporarily boost the refresh rate from the secondapplication 206 b, and calls the scheduler 218 to execute the temporaryboost.

In operation 509, the scheduler 218 determines the frequency for eachexecuting application 206. In some implementations, determining thefrequency includes identifying each executing application 206 within theVSync framework 220 as either opted in to the non-virtualized frequency222 or not opted in to the non-virtualized frequency 222 and thereforeoperating under the virtualized frequency 224. For example, the secondapplication 206 b is reassigned to the non-virtualized frequency 222responsive to the request to temporarily boost the refresh rate.

Following the determination of whether each executing application 206 isopted in to the non-virtualized frequency 222 or not opted in to thenon-virtualized frequency 222, the scheduler 218 initiates the temporaryboosting of the refresh rate of the user interface 216. For example, inoperation 511 the scheduler 218 sends a vblank, at an intervalcorresponding to the lower frequency, to applications executing at boththe non-virtualized frequency 222 and the virtualized frequency 224, andthen in operation 513 the scheduler 218 sends a vblank at an intervalcorresponding to the higher frequency to applications executing at onlythe non-virtualized frequency 222. For example, as described in thedescription of FIGS. 3 and 4 , at a first time such as 100 ms, a vblank332 is sent to applications 206 executing at the non-virtualizedfrequency 222 and at the virtualized frequency 224, at a second timesuch as 108 ms, a vblank 334 is sent to applications 206 executing atthe non-virtualized frequency 222 only, and at a third time such as 106ms, a vblank 336 is sent to applications 206 executing at both thenon-virtualized frequency 222 and the virtualized frequency 224, and soforth. Operations 507 and 509 may repeat until the conclusion of thetemporary boosting period.

In operation 515, the second application 206 b sends a request to theprocessor 208 to cease the temporary boosting of the refresh rate, orunboost. The second applications 206 b may send the request to unboostfor one of several different reasons. In one implementation, the secondapplication 206 b determines to unboost based on not receivingadditional input for a predetermined amount of time. For example, wherea predetermined amount of time passes without the second application 206b receiving an input, the second application 206 b automatically sends arequest to the processor 208 to unboost. In other implementations, theinitial request to boost may be intended as a request to boost for aparticular period of time, and upon the expiration of the particularperiod of time, the second application 206 b automatically sends arequest to the processor 208 to unboost. In still other implementations,the second application 206 b opts to return to the baseline refresh rateto lessen the impact on the system 200. For example, one or moreapplications 206 may include functionality to determine when requests totemporarily boost the refresh rate are sent and/or rescinded. Forexample, an application 206 may include functionality to send and/orrescind a request to temporarily boost the refresh rate when theapplication 206 determines to do so would provide a visual benefit onthe user interface 216, such as scrolling, panning, or receiving aninput, or when there is a power pertinent reason for holding back therefresh rate to an unboosted rate.

In operation 517, the processor 208 determines to cease the temporaryboosting of the refresh rate of the user interface 216 based on thereception of a request to cease the temporary boosting from one or moreof the applications 206 executing at the non-virtualized frequency 222.In some implementations, the processor 208 determines to cease thetemporary boosting based on all other boosting requests having beencanceled and the processes of those applications 206 remaining active,and the request transmitted from the second application 206 b being thefinal request to cease the temporary boosting. In other words, theprocessor 208 determines to cease the temporary boosting if and only ifno other boosting requests are open.

In operation 519, the processor 208 controls the user interface 216 toreturn to the original refresh rate and ceases the temporary boosting ofthe refresh rate. In other words, each of the applications 206 presentedon the user interface 216 return to refreshing, or updating, on thebaseline frequency. Following operation 413, each application 206presented on the user interface 216 receives the next vblank at thelower, baseline frequency, which is the same as the virtualizedfrequency 224.

It should be understood that as shown in FIGS. 5A and 5B, the secondapplication 206 b receives an input, sends the boost request, and sendsthe unboost request. However, these examples are provided forillustration only and should not be construed as limiting. Variousexamples are possible without departing from the scope of the presentdisclosure. For example, the first application 206 a may also be anexample of an application that receives an input, based on the receptionof the input, sends a boost request to the processor 208, and ultimatelysends an unboost request to the processor 208. In anotherimplementation, each of the first and second applications 206 a, 206 breceive inputs and send boost requests. For example, the secondapplication 206 b may receive an input and opt in to the temporaryboost. In the midst of the duration of the temporary boosting inoperations 511 and 513, the first application 206 a receives an inputand sends a request to temporarily boost the refresh rate. The scheduler218 detects a change in the status of the first application 206 a, asthe first application 206 a has now opted in to temporarily boosting therefresh rate, upon the first application 206 a sending the request totemporarily boost the refresh rate and updates the VSync framework 220to include the first application 206 a as executing on thenon-virtualized frequency 222. The scheduler 218 then sends thenon-virtualized vblanks to each of the first application 206 a and thesecond application 206 b throughout the period of temporary boosting.Furthermore, the processor 208 may not determine to cease the refreshrate boosting in operation 517 until a request to cease the temporaryboosting is received from each of the first application 206 a and thesecond application 206 b.

FIG. 6 illustrates an example system including applications displayed onmore than one display according to various examples of the presentdisclosure. The system 600 includes a first display 601 and a seconddisplay 603. As shown in the system 600, the first display 601 and asecond display 603 may collectively be referred to as the user interface216.

As described herein, each of the first display 601 and the seconddisplay 603 may be a monitor, a laptop display, a touch screen, or anyother suitable display device to present content 207. One or both of thefirst display 601 and the second display 603 may be an in planeswitching (IPS) liquid-crystal display (LCD), an LCD without IPS, anorganic light-emitting diode (OLED) screen, or any other suitable typeof display. In some implementations, one or both of the first display601 and the second display 603 may include a touch screen such that therespective display may directly receive an input, such as from a stylusor from the finger of a user of the system 200. One or both of the firstdisplay 601 and the second display 603 may support various interactions,such as panning, scrolling, zooming in, zooming out, inking, and soforth.

As shown in FIG. 6 , the first display 601 presents one or moreapplications, such as the first application 206 a, and the seconddisplay 603 presents one or more applications, such as the secondapplication 206 b and the third application 206 n. However, theseexamples should not be construed as limiting. Various examples arepossible. The system 600 may include more or fewer than two displays todisplay content 207. In some implementations, the first display 601displays content 207 corresponding to more than one application or zeroapplications. In some implementations, the second display 603 displayscontent 207 corresponding to less than two applications, noapplications, or more than two applications. Each of the respectivedisplays 601, 603 may display content 207 in various display formats.For example, one application 206 may be presented in a full-screen mode,where the entire display displays content 207 corresponding to the oneapplication 206, two or more applications 206 may be presented in asplit-screen mode, where each application 206 is presented on less thanthe entire display but the entire display displays content 207corresponding to the applications 206, or a partial-screen mode, whereat least one application is presented on the display but on less thanthe entire display such that other applications may be at leastpartially viewed and interacted with.

In some implementations, one of the first display 601 and the seconddisplay 603 is characterized as the primary display. The primary displaymay be characterized as such either by a user selection or automaticallyselected by the processor 208. For example, the processor 208 maycharacterize the primary display as the display having a higher maximumrefresh rate, the display having a larger size, or any other suitablemethods. The primary display may be automatically characterized, oridentified, by the processor 208 each time a new display is connected,each time a new display is removed, each time the system 200 is turnedon, each time the system 200 is connected to the network, or at apredetermined interval. The primary display may also be characterized,or identified, by a user selection at any time to override the automaticselection by the processor 208.

Each of the first display 601 and the second display 603 are configuredwith manufacturer settings that control a maximum refresh rate supportedby the respective display. For example, each of the first display 601and the second display 603 may have a maximum refresh rate of 60 Hz, 120Hz, or any other suitable refresh rate. In some implementations, thefirst display 601 and the second display 603 have the same maximumrefresh rate. For example, each of the first display 601 and the seconddisplay 603 may have a maximum refresh rate of 60 Hz or 120 Hz. In otherimplementations, the first display 601 and the second display 603 havedifferent maximum refresh rates. For example, the first display 601 mayhave a maximum refresh rate of 60 Hz while the second display 603 mayhave a maximum refresh rate of 120 Hz.

As described herein, the availability of dynamic refresh rate temporaryboosting depends on the compatibility of components of the particularsystem 200 executing the one or more applications, such as instructions204 and the user interface 216 displaying the content 207 of theparticular application at the time. For example, as shown in FIG. 6 ,the first display 601 displays content 207 of the first application 206a. For the processor 208 to temporarily boost the refresh rate of thefirst application 206 a, the first application 206 a must be opted in todynamic refresh rate switching, i.e., must have opted in to operateunder the non-virtualized frequency 222, and the first display 601 mustsupport the boosted refresh rate. The opting in to the dynamic refreshrate switching may be implicit, such as by construction of theapplication 206, or explicit, such as by the sending of signalindicating the status of the application 206 as opted in. In someimplementations, dynamic refresh rate temporary boosting is notavailable for any displays of the user interface 216 if the displaycharacterized as the primary display does not support the boostedrefresh rate.

In one implementation, the first display 601 does not support theboosted refresh rate, while the second display 603 does support theboosted refresh rate. The second display 603 displaying the secondapplication 206 b and the third application 206 n is characterized asthe primary display. The first display 601 displaying the firstapplication 206 a is thus characterized as a secondary, i.e.,non-primary, display. Because the first display 601 does not support theboosted refresh rate, the first application 206 a renders each frame atthe rate of the primary display, i.e., the second display 603, but therendered frames are presented on the first display 601 at the maximumrefresh rate of the first display 601, for example the unboosted refreshrate. The second application 206 b is opted in to temporary boosting,but the third application 206 n is not opted in to temporary boosting.The second application 206 b transmits a boosting request to theprocessor 208, for example based on receiving an input on the seconddisplay 603, such as a touch input, scrolling, panning, zooming in,zooming out, or inking. As described herein, the processor 208 receivesthe request to temporarily boost the refresh rate, determines totemporarily boost the refresh rate, and controls the scheduler 218 todetermine the opted frequency for each executing application on displaysthat support the boosted refresh rate. Based on the aforementionedopting preferences of the second application 206 b and the thirdapplication 206 n, the scheduler 218 identifies the second application206 b as executing on the non-virtualized frequency 222 and the thirdapplication 206 n as executing on the virtualized frequency 224.Therefore, the second application 206 b receives clock notifications atthe non-virtualized frequency 222 and the third application 206 nreceives clock notifications at the virtualized frequency 224 asdescribed in greater detail with reference to the description of FIG. 3. Accordingly, the refresh rate of the second display 603 is temporarilyboosted to the higher refresh rate, enabling the second application 206b to refresh at a higher rate for the duration of the temporary boostingand enabling the third application 206 n to continue refreshing at avirtual rate consistent with its capability.

At a later time, the second application 206 b transmits a request tocease, or terminate, the temporary boosting of the refresh rate. Forexample, the second application 206 b may no longer be activelyreceiving the input that prompted the request to temporarily boost therefresh rate. Upon receiving the request, the processor 208 determineswhether to cease the temporary boosting. For example, the processor 208may scan the queue 228 of boosting requests to determine whether anyboosting requests remain open, i.e., have not been terminated or closed.Where no open boost requests are identified in the queue 228, theprocessor 208 terminates the temporary boosting and the secondapplication 206 b returns to executing at the original refresh rate.Where other boost requests are identified in the queue 228, theprocessor 208 cancels the boost request of the second application 206 bbut does not terminate the temporary boost of the user interface 216. Inthis example, the second application 206 b may be transferred within theV Sync framework 220 to the virtualized frequency 224 and continuerefreshing at the original refresh rate.

FIG. 7 is a flow chart illustrating a computer-implemented method ofdynamic refresh rate switching according to various examples of thepresent disclosure. The operations illustrated in FIG. 7 are forillustration and should not be construed as limiting. Various examplesof the operations may be used without departing from the scope of thepresent disclosure. The operations of the flow chart 700 may be executedby one or more components of the system 200, including the processor208, the scheduler 218, the first application 206 a, and the secondapplication 206 b.

The flow chart 700 begins by the processor 208 presenting a firstapplication 206 a and a second application 206 b on a user interface 216in operation 701. The first application 206 a and a second application206 b initially execute at a first refresh rate. In operation 703, theprocessor 208 receives, from the second application 206 b, a request totemporarily boost the first refresh rate to a second refresh rate. Thesecond refresh rate is higher than the first refresh rate.

In operation 705, the processor 208 determines whether to temporarilyboost the refresh rate to the second refresh rate. In someimplementations, the processor 208 determines to temporarily boost therefresh rate to the second refresh rate based on the receipt of a firstrequest to boost from an application. In other implementations, theprocessor 208 scans the queue 228 for open boost requests andtemporarily boosts the refresh rate only when a predetermined number ofrequests to boost have been received. Where the processor 208 determinesnot to boost the refresh rate, the processor 208 returns to operation701 and continues to present the first application 206 a and a secondapplication 206 b on the user interface 216 at the first refresh rate.Where the processor 208 determines to boost the refresh rate, theprocessor 208 proceeds to operation 707.

In operation 707, the processor 208 controls the scheduler 218 toidentify the executing application 216 as opted in to executing at theboosted refresh rate or not opted in. For example, the scheduler 218identifies the second application 206 b as opted in to the secondrefresh rate and identifies the first application 206 a as not opted into the second refresh rate. In operation 709, the scheduler 218transmits a first signal to the first application 206 a to refresh firstcontent 207 a presented on the user interface 216 at the first refreshrate and transmits a second signal to the second application 206 b torefresh second content 207 b presented on the user interface 216 at thesecond refresh rate. The first signal is a virtualized pulse indicatinga new frame corresponding to the first refresh rate and the secondsignal is a non-virtualized pulse indicating a new frame correspondingto the second refresh rate. In some implementations, the first signaland the second signal are the same signal, such as a vblank indicatingto refresh the content presented on the user interface 216, buttransmitted with different timing. In operation 711, the firstapplication 206 a refreshes the first content 207 a upon receipt of thefirst signal and the second application 206 b refreshes the secondcontent 207 b upon receipt of the second signal.

Additional Examples

Some examples herein are directed to a method of dynamically updating arefresh rate, as illustrated by the flow chart 700. The method (700)includes presenting (701) a first application (206 a) and a secondapplication (206 b) on at least one user interface (216), each of thefirst application and the second application executing at a firstrefresh rate; receiving (703), from the second application, a request totemporarily boost the first refresh rate to a second refresh rate,wherein the second refresh rate is higher than the first refresh rate;responsive to receiving the request, determining (705) to temporarilyboost the first refresh rate to a second refresh rate; identifying(707), by a scheduler (218), the second application as opted in to thesecond refresh rate and identifying the first application as not optedin to the second refresh rate; transmitting (709), by the scheduler, afirst signal (332) to the first application to refresh first content(207 a) presented on the user interface at the first refresh rate andtransmitting, by the scheduler, a second signal (334) to the secondapplication to refresh second content (207 b) presented on the userinterface at the second refresh rate, wherein the first signal is avirtualized pulse indicating a new frame corresponding to the firstrefresh rate and wherein the second signal is a non-virtualized pulseindicating a new frame corresponding to the second refresh rate; andcontrolling the first application to refresh (711) the first content atthe first refresh rate upon receipt of the first signal and controllingthe second application to refresh the second content at the secondrefresh rate upon receipt of the second signal.

In some examples, the method further includes receiving a request, fromthe second application, to terminate the temporary boost to the secondrefresh rate.

In some examples, the method further includes, responsive to receivingthe request to terminate the temporary boost, scanning a queue (228) ofboost requests to identify any open boost requests, and based onidentifying no open boost requests, terminating the temporary boost suchthat the second application returns to executing at the first refreshrate.

In some examples, the method further comprises accessing a virtualframework (220), and identifying the second application as opted in tothe second refresh rate and identifying the first application as notopted in to the second refresh rate by identifying the first applicationand the second application within the virtual framework.

In some examples, the method further comprises receiving, from thesecond application, a request to opt in to the second refresh rate,wherein opting in to the second refresh rate includes opting to receiveclock (226) notifications at a higher frequency than the first refreshrate.

In some examples, a frequency of the second refresh rate is an integermultiple of the first refresh rate.

In some examples, receiving, from the second application, the request totemporarily boost the refresh rate includes receiving the request basedat least in part on the second application receiving an input on theuser interface.

In some examples, the received input comprises one or more of panning,scrolling, zooming in, zooming out, and inking.

Although described in connection with an example computing device 100and system 200, examples of the disclosure are capable of implementationwith numerous other general-purpose or special-purpose computing systemenvironments, configurations, or devices. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with aspects of the disclosure include, but are notlimited to, servers, smart phones, mobile tablets, mobile computingdevices, personal computers, server computers, hand-held or laptopdevices, multiprocessor systems, gaming consoles, microprocessor-basedsystems, set top boxes, programmable consumer electronics, mobiletelephones, mobile computing and/or communication devices in wearable oraccessory form factors (e.g., watches, glasses, headsets, or earphones),network PCs, minicomputers, mainframe computers, distributed computingenvironments that include any of the above systems or devices, virtualreality (VR) devices, augmented reality (AR) devices, mixed reality (MR)devices, holographic device, and the like. Such systems or devices mayaccept input from the user in any way, including from input devices suchas a keyboard or pointing device, via gesture input, proximity input(such as by hovering), and/or via voice input.

Examples of the disclosure may be described in the general context ofcomputer-executable instructions, such as program modules, executed byone or more computers or other devices in software, firmware, hardware,or a combination thereof. The computer-executable instructions may beorganized into one or more computer-executable components or modules.Generally, program modules include, but are not limited to, routines,programs, objects, components, and data structures that performparticular tasks or implement particular abstract data types. Aspects ofthe disclosure may be implemented with any number and organization ofsuch components or modules. For example, aspects of the disclosure arenot limited to the specific computer-executable instructions or thespecific components or modules illustrated in the figures and describedherein. Other examples of the disclosure may include differentcomputer-executable instructions or components having more or lessfunctionality than illustrated and described herein. In examplesinvolving a general-purpose computer, aspects of the disclosuretransform the general-purpose computer into a special-purpose computingdevice when configured to execute the instructions described herein.

By way of example and not limitation, computer readable media comprisecomputer storage media and communication media. Computer storage mediainclude volatile and nonvolatile, removable, and non-removable memoryimplemented in any method or technology for storage of information suchas computer readable instructions, data structures, program modules, orthe like. Computer storage media are tangible and mutually exclusive tocommunication media. Computer storage media are implemented in hardwareand exclude carrier waves and propagated signals. Computer storage mediafor purposes of this disclosure are not signals per se. Exemplarycomputer storage media include hard disks, flash drives, solid-statememory, phase change random-access memory (PRAM), static random-accessmemory (SRAM), dynamic random-access memory (DRAM), other types ofrandom-access memory (RAM), read-only memory (ROM), electricallyerasable programmable read-only memory (EEPROM), flash memory or othermemory technology, compact disk read-only memory (CD-ROM), digitalversatile disks (DVD) or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other non-transmission medium that may be used to storeinformation for access by a computing device. In contrast, communicationmedia typically embody computer readable instructions, data structures,program modules, or the like in a modulated data signal such as acarrier wave or other transport mechanism and include any informationdelivery media.

The order of execution or performance of the operations in examples ofthe disclosure illustrated and described herein is not essential and maybe performed in different sequential manners in various examples. Forexample, it is contemplated that executing or performing a particularoperation before, contemporaneously with, or after another operation iswithin the scope of aspects of the disclosure. When introducing elementsof aspects of the disclosure or the examples thereof, the articles “a,”“an,” “the,” and “said” are intended to mean that there are one or moreof the elements. The terms “comprising,” “including,” and “having” areintended to be inclusive and mean that there may be additional elementsother than the listed elements. The term “exemplary” is intended to mean“an example of” The phrase “one or more of the following: A, B, and C”means “at least one of A and/or at least one of B and/or at least one ofC.”

Having described aspects of the disclosure in detail, it will beapparent that modifications and variations are possible withoutdeparting from the scope of aspects of the disclosure as defined in theappended claims. As various changes could be made in the aboveconstructions, products, and methods without departing from the scope ofaspects of the disclosure, it is intended that all matter contained inthe above description and shown in the accompanying drawings shall beinterpreted as illustrative and not in a limiting sense.

While no personally identifiable information is tracked by aspects ofthe disclosure, examples have been described with reference to datamonitored and/or collected from the users. In some examples, notice maybe provided to the users of the collection of the data (e.g., via adialog box or preference setting) and users are given the opportunity togive or deny consent for the monitoring and/or collection. The consentmay take the form of opt-in consent or opt-out consent.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

It will be understood that the benefits and advantages described abovemay relate to one example or may relate to several examples. Theexamples are not limited to those that solve any or all of the statedproblems or those that have any or all of the stated benefits andadvantages. It will further be understood that reference to ‘an’ itemrefers to one or more of those items.

The term “comprising” is used in this specification to mean includingthe feature(s) or act(s) followed thereafter, without excluding thepresence of one or more additional features or acts.

In some examples, the operations illustrated in the figures may beimplemented as software instructions encoded on a computer readablemedium, in hardware programmed or designed to perform the operations, orboth. For example, aspects of the disclosure may be implemented as asystem on a chip or other circuitry including a plurality ofinterconnected, electrically conductive elements.

The order of execution or performance of the operations in examples ofthe disclosure illustrated and described herein is not essential, unlessotherwise specified. That is, the operations may be performed in anyorder, unless otherwise specified, and examples of the disclosure mayinclude additional or fewer operations than those disclosed herein. Forexample, it is contemplated that executing or performing a particularoperation before, contemporaneously with, or after another operation iswithin the scope of aspects of the disclosure.

What is claimed is:
 1. A system comprising: a processor; a firstapplication and a second application; a user interface configured topresent the first application and the second application, each of thefirst application and the second application executing at a firstrefresh rate; and a memory storing instructions that, when executed bythe processor, causes the processor to: determine to temporarily boostthe first refresh rate to a second refresh rate, wherein the secondrefresh rate is higher than the first refresh rate, transmit a firstsignal to the first application to refresh first content presented onthe user interface at the first refresh rate, wherein the first signalis transmitted in accordance with a virtualized refresh rate, transmit asecond signal to the second application to refresh second contentpresented on the user interface at the second refresh rate, wherein thesecond signal is transmitted in accordance with a non-virtualizedrefresh rate, and control the first application to refresh the firstcontent at the first refresh rate upon receipt of the first signal, andthe second application to refresh the second content at the secondrefresh rate upon receipt of the second signal.
 2. The system of claim 1wherein the memory further stores instructions that, when executed bythe processor, cause the processor to: receive a request, from thesecond application, to terminate the temporary boost to the secondrefresh rate.
 3. The system of claim 2 wherein the memory further storesinstructions that, when executed by the processor, cause the processorto: responsive to receiving the request to terminate the temporaryboost, scan a queue of boost requests to identify any open boostrequests, and terminate the temporary boost such that the secondapplication returns to executing at the first refresh rate.
 4. Thesystem of claim 1 wherein the instructions further cause the processorto: identify the second application as opted in to the second refreshrate and identify the first application as not opted in to the secondrefresh rate.
 5. The system of claim 4 wherein the instructions furthercause the processor to: wherein the second application is configured toopt in to the second refresh rate by opting to receive clocknotifications at a higher frequency than the first refresh rate.
 6. Thesystem of claim 1 wherein a frequency of the second refresh rate is aninteger multiple of the first refresh rate.
 7. The system of claim 1,wherein the second application is configured to send a request totemporarily boost the first refresh rate based at least in part onreceiving an input on the user interface.
 8. The system of claim 7wherein the received input comprises one or more of panning, scrolling,zooming in, zooming out, and inking.
 9. The system of claim 1 wherein:the first signal is a virtualized pulse indicating a new framecorresponding to the first refresh rate, and the second signal is anon-virtualized pulse indicating a new frame corresponding to the secondrefresh rate.
 10. The system of claim 1 wherein the user interface ispresented on a first monitor that presents the first application and asecond monitor that presents the second application.
 11. Acomputer-implemented method comprising: presenting a first applicationand a second application, each of the first application and the secondapplication executing at a first refresh rate; responsive to receiving arequest from the second application to temporarily boost the firstrefresh rate, determining to temporarily boost the first refresh rate toa second refresh rate, wherein the second refresh rate is higher thanthe first refresh rate; transmitting a first signal to the firstapplication to refresh first content presented on a user interface atthe first refresh rate, wherein the first signal is transmitted inaccordance with a virtualized refresh rate; transmitting a second signalto the second application to refresh second content presented on theuser interface at the second refresh rate, wherein the second signal istransmitted in accordance with a non-virtualized refresh rate; andcontrolling the first application to refresh the first content at thefirst refresh rate upon receipt of the first signal, and the secondapplication to refresh the second content at the second refresh rateupon receipt of the second signal.
 12. The computer-implemented methodof claim 11 further comprising: receiving a request, from the secondapplication, to terminate the temporary boost to the second refreshrate; responsive to receiving the request to terminate the temporaryboost, scanning a queue of boost requests to identify any open boostrequests; and based on identifying no open boost requests, terminatingthe temporary boost such that the second application returns toexecuting at the first refresh rate.
 13. The computer-implemented methodof claim 11 further comprising: identifying the second application asopted in to the second refresh rate and identify the first applicationas not opted in to the second refresh rate.
 14. The computer-implementedmethod of claim 13 wherein the second application is configured to optin to the second refresh rate by opting to receive clock notificationsat a higher frequency than the first refresh rate.
 15. Thecomputer-implemented method of claim 11 wherein a frequency of thesecond refresh rate is an integer multiple of the first refresh rate.16. The computer-implemented method of claim 11 wherein the secondapplication is configured to send a request to temporarily boost thefirst refresh rate based at least in part on receiving an input on theuser interface.
 17. The computer-implemented method of claim 11 wherein:the first signal is a virtualized pulse indicating a new framecorresponding to the first refresh rate, and the second signal is anon-virtualized pulse indicating a new frame corresponding to the secondrefresh rate.
 18. One or more computer-storage memory devices embodiedwith executable instructions that, when executed by a processor, causethe processor to: present a first application and a second application,each of the first application and the second application executing at afirst refresh rate; responsive to receiving a request from the secondapplication to temporarily boost the first refresh rate, determine totemporarily boost the first refresh rate to a second refresh rate,wherein the second refresh rate is higher than the first refresh rate;transmit a first signal to the first application to refresh firstcontent presented on a user interface at the first refresh rate, whereinthe first signal is transmitted in accordance with a virtualized refreshrate; transmit a second signal to the second application to refreshsecond content presented on the user interface at the second refreshrate, wherein the second signal is transmitted in accordance with anon-virtualized refresh rate; and control the first application torefresh the first content at the first refresh rate upon receipt of thefirst signal, and the second application to refresh the second contentat the second refresh rate upon receipt of the second signal.
 19. Theone or more computer-storage memory devices of claim 18, wherein theprocessor further: receives a request, from the second application, toterminate the temporary boost to the second refresh rate; responsive toreceiving the request to terminate the temporary boost, scans a queue ofboost requests to identify any open boost requests; and based onidentifying no open boost requests, terminates the temporary boost suchthat the second application returns to executing at the first refreshrate.
 20. The one or more computer-storage memory devices of claim 18,wherein the processor further: identifies the second application asopted in to the second refresh rate and identify the first applicationas not opted in to the second refresh rate, wherein the secondapplication is configured to opt in to the second refresh rate by optingto receive clock notifications at a higher frequency than the firstrefresh rate.